We've been spamming feature/dynamodbstreams/attributevalue releases, this fixes that.

why

feature/dynamodbstreams is copied from feature/dynamodb as part of make recipe copy-attributevalue-feature - so whenever you update one, you technically also update the other. This happens on release.

That includes the go_module_metadata.go file from the source module. At some point in the past few months the committed versions for these two files got desynced. So every release, this has been happening:

• release runs make generate - nothing changes in the streams version except for go_module_metadata.go
• release system goes "hey, contents of feature/dynamodbstreams/attributevalue changed - new release!"
• release annotation runs, updating tags and module versions - which upon seeing no changelog entry in ddb streams, just does the default patch version bump, inserting a dummy changelog that says "no notes"
  • that process involves setting the value in go_module_metadata.go to the new version. so the incidental copy, which triggered this whole thing in the first place, is overwritten. rinse and repeat

testing

Tested by running make generate with:

• nothing changed in dynamodb/attributevalue. verified that the module metadata file stream-side didn't update this time.
• some dummy change in dynamodb/attributevalue. verified that it still gets copied